Transmission Power Determination for Transport Block Repetitions

ABSTRACT

In some embodiments, a wireless device receives a power offset value associated with a difference between transmission powers of different redundancy versions (RVs) of repetition occasions of a transport block. A downlink control information is received that indicates: a sequence of RVs, and a quantity of the repetition occasions. Based on the power offset value and the RVs, a transmission power is determined for one or more repetition occasions of the repetition occasions. One or more repetitions of the transport block are transmitted with the determined transmission power via the one or more repetition occasions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/149,154, filed Jan. 14, 2021, which claims the benefit of U.S. Provisional Application No. 62/961,267, filed Jan. 15, 2020, the contents of each of which are hereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure and location.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communication with a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

FIG. 17A is an example of redundancy version (RV) indication for multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure.

FIG. 17B is an example of rate matching for different redundancy versions (RVs) as per an aspect of an embodiment of the present disclosure.

FIG. 17C is an example of a redundancy version (RV) indication for multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example of beam management for codebook-based uplink transmission with multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure.

FIG. 19 is an example of beam management for non-codebook-based uplink transmission with multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure.

FIG. 20 is an example of uplink transmission with multiple repetition transmission occasions and multiple redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 21A is an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 21B is an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 21C is an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 21D is an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example of a power control procedure for uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 23 is an example of a power control procedure for uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 24A is an example of a MAC CE for power offset value selection as per an aspect of an embodiment of the present disclosure.

FIG. 24B is a flow chart of an example method for power control for an uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example of an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure.

FIG. 26 is an example of a power control procedure for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure.

FIG. 27A is an example of power control parameter indication for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure.

FIG. 27B is an example of power control parameter indication for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure.

FIG. 28 is a flow chart of an example method for power control for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and/or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of” provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and/or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle road side unit (RSU), relay node, automobile, and/or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and/or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and/or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and/or 5G standards), an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard), and/or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.

In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and/or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF/UPF 158 in FIG. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra-/inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and/or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and/or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNB s, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and/or one or more ng-eNB s, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and/or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and/or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and/or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or more AMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF/UPF nodes to provide redundancy and/or to load share across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and/or error rate). The SDAPs 215 and 225 may perform mapping/de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping/de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering/deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map/de-map the split radio bearer between RLC channels belonging to cell groups.

The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logical channels and/or mapping between logical channels and transport channels. The multiplexing/demultiplexing may include multiplexing/demultiplexing of data units, belonging to the one or more logical channels, into/from Transport Blocks (TB s) delivered to/from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and/or padding. The MACs 212 and 222 may support one or more numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding/decoding and modulation/demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet. The data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g., with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages         used to page a UE whose location is not known to the network on         a cell level;     -   a broadcast control channel (BCCH) for carrying system         information messages in the form of a master information block         (MIB) and several system information blocks (SIBs), wherein the         system information messages may be used by the UEs to obtain         information about how a cell is configured and how to operate         within the cell;     -   a common control channel (CCCH) for carrying control messages         together with random access;     -   a dedicated control channel (DCCH) for carrying control messages         to/from a specific the UE to configure the UE; and     -   a dedicated traffic channel (DTCH) for carrying user data         to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

-   -   a paging channel (PCH) for carrying paging messages that         originated from the PCCH;     -   a broadcast channel (BCH) for carrying the MIB from the BCCH;     -   a downlink shared channel (DL-SCH) for carrying downlink data         and signaling messages, including the SIBs from the BCCH;     -   an uplink shared channel (UL-SCH) for carrying uplink data and         signaling messages; and     -   a random access channel (RACH) for allowing a UE to contact the         network without any prior scheduling.

The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1/L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from         the BCH;     -   a physical downlink shared channel (PDSCH) for carrying downlink         data and signaling messages from the DL-SCH, as well as paging         messages from the PCH;     -   a physical downlink control channel (PDCCH) for carrying         downlink control information (DCI), which may include downlink         scheduling commands, uplink scheduling grants, and uplink power         control commands;     -   a physical uplink shared channel (PUSCH) for carrying uplink         data and signaling messages from the UL-SCH and in some         instances uplink control information (UCI) as described below;     -   a physical uplink control channel (PUCCH) for carrying UCI,         which may include HARQ acknowledgments, channel quality         indicators (CQI), pre-coding matrix indicators (PMI), rank         indicators (RI), and scheduling requests (SR); and     -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

2.2 Control Plane Protocol Stack

FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNB s 160 or ng-eNB s 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3 μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and/or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and/or an initiation of random access.

FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and/or in response receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response receiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same/similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same/similar manner as the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to/from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and/or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and/or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and/or RI) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same/similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment/grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS)/physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure and location. A burst of SS/PBCH blocks may include one or more SS/PBCH blocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11A is an example, and that these parameters (number of SS/PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS/PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS/PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS/PBCH block, the locations of the SSS and the PBCH, respectively. The SS/PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection/search and/or reselection may be based on the CD-SSB.

The SS/PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS/PBCH block. For example, the SS/PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS/PBCH block in the transmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and/or a SS/PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS/PBCH block at the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCH block transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS/PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.

In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS/PBCH blocks. In an example, a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks. The PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and/or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and/or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and/or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and/or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation/channel estimation of the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time/frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and/or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in a SRS resource set of the one or more SRS resource sets (e.g., with the same/similar time domain behavior, periodic, aperiodic, and/or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and/or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/or subframe level periodicity; offset for a periodic and/or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters.

Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and/or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resource parameters.

The three beams illustrated in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and/or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and/or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). The UE and/or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and/or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counter-clockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and/or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and/or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and/or the like).

The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS/PBCH blocks, one or more CSI-RS resources, and/or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and/or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and/or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and/or an RRC_INACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and/or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and/or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and/or for establishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 may include and/or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and/or be referred to as a random access response (RAR).

The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and/or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and/or in an RRC_INACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and/or an uplink transmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS/PBCH blocks and/or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS/PBCH blocks mapped to a PRACH occasion and/or a number of preambles mapped to a SS/PBCH blocks.

The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and/or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and/or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and/or CSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and/or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and/or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and/or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and/or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and/or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and/or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0≤t_id<80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier). The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 4 1314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and/or switch an uplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on a channel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 3 1313 and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and/or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321. The UE may receive, from the base station via PDCCH and/or RRC, an indication of a preamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and/or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and/or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and/or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and/or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and/or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated in FIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and/or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and/or the like); whether the UE has valid TA or not; a cell size; the UE's RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and/or an uplink transmit power for the preamble 1341 and/or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and/or a power control for the preamble 1341 and/or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and/or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and/or an MCS); a UE identifier for contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and/or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The control signaling may be referred to as L1/L2 control signaling and may originate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and/or uplink control signaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and/or a transport format; a slot format information; a preemption indication; a power control command; and/or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and/or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and/or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling and/or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and/or configured for a PDCCH. Based on a payload size of the DCI and/or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and/or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and/or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and/or more than one base station, with the same or similar configuration as those shown in FIG. 15.

The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and/or some combination of the two duplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and/or the like.

As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit/receive diversity, and/or beamforming. In other examples, the wireless device 1502 and/or the base station 1504 may have a single antenna.

The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and/or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and/or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

The processing system 1508 and/or the processing system 1518 may comprise one or more controllers and/or one or more processors. The one or more controllers and/or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and/or the processing system 1518 may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

The processing system 1508 and/or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and/or hardware that provide features and/or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and/or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and/or the like). The processing system 1508 and/or the processing system 1518 may receive user input data from and/or provide user output data to the one or more peripherals 1516 and/or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and/or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and/or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, an CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual-connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period/window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period/window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

When supporting ultra-reliable low latency communication (URLLC) services, a wireless device may be indicated by a base station, via one or more indications, with multiple repetition transmission occasions (TOs) of an uplink transport block. In an example, the one or more indications may comprise one or more RRC messages, for example, pusch-AggregationFactor being larger than 1 may be configured by the base station to the wireless device via RRC message(s). In an example, the one or more indications may comprise one or more downlink control information (DCIs), for example, the multiple repetition TOs may be indicated by the base station to the wireless device via a DCI. In an example, the one or more indications may comprise one or more RRC messages and one or more DCIs, for example, the base station may configure multiple numbers of repetition TOs to the wireless device via an RRC message. The base station may indicate one of the multiple numbers of repetition transmission occasions to the wireless device via a DCI and/or a MAC CE. A same symbol allocation may be applied across the multiple repetition TOs for the wireless device. The wireless device may repeat the uplink transport block within each symbol allocation among each of the multiple repetition TOs. The wireless device may apply a redundancy version on a n^(th) repetition transmission occasion (TO) of the multiple repetition TOs for the uplink transport block as shown in FIG. 17A. In an example, when the base station indicates a redundancy version indication (e.g., rv_(id)=0) to the wireless device via a DCI, the wireless device may determine the redundancy version is 0 in response to n modulo 4 being equal to 0. The wireless device may determine the redundancy version is 2 in response to n modulo 4 being equal to 1. The wireless device may determine the redundancy version is 3 in response to n modulo 4 being equal to 2. The wireless device may determine the redundancy version is 1 in response to n modulo 4 being equal to 3. A same rule may be applied for other redundancy version indications (e.g., rv_(id)=1, 2, or 3). In an example, the DCI comprising the redundancy version may indicate the multiple repetition TOs to the wireless device.

A wireless device may perform rate-matching functionality to extract a suitable number of coded bits to match resources assigned for a transmission required for the hybrid-ARQ protocol. A wireless device may perform rate-matching functionality to generate different redundancy versions (RVs) required for the hybrid-ARQ protocol. In an example, a number of bits to be transmitted on a PUSCH may depend on a plurality of factors. The plurality of factors may comprise a number of resources blocks scheduled, a number of OFDM symbols scheduled, and amount of overlapping resource elements used for other purposes (e.g., reference signals, control channels, or system information). In an example, the amount of overlapping resource element may depend on reserved resources to provide new features/compatibility. The wireless device may perform rate matching for each code block of the uplink transport block. In an example, as shown in FIG. 17B, the wireless device may store coded bits into a circular buffer. The coded bits may start with non-punctured systematic bits and continue with parity bits. The wireless device may select transmission bits based on taking/fetching a required number of bits from the circular buffer. The exact selected bits for transmission may depend on a redundancy version (RV) (e.g., RV0, RV1, RV2 or RV3) corresponding to a different starting position in the circular buffer. The wireless device, by selecting a different RV, may generate different set of coded bits representing a same set of information bits of the uplink transport block. The different starting positions in the circular buffer may be defined such that both RV0 and RV3 are self-decodable (e.g., RV0 and RV3 may comprise systematic bits under typical scenarios).

The base station may perform a soft combining to decode the uplink transport block with retransmission (or with multiple repetition TOs) via different RVs. The rate-matching functionality may comprise interleaving coded bits using a block interleaver and collecting coded bits from each code block. The coded bits from the circular buffer may be written row-by-row into a block interleaver and read out column-by-column. The number of rows in the interleaver may be determined by modulation order. Coded bits in one column may correspond to one modulation symbol. The systematic bits may spread across the modulation symbols to improve system performance. Bit collection may concatenate coded bits for each code block. In an example, as shown in FIG. 17C, the base station may indicate eight repetition TOs to the wireless device via an RRC message and/or a DCI (e.g., the configured pusch-AggregationFactor via RRC message(s) may be eight slots, or eight repetition TOs may be indicated by the base station via a DCI). When the base station indicates the wireless device a redundancy version indication (e.g., RV=00) via a DCI in PDCCH, the wireless device may determine the redundancy versions (RVs) in order of 0, 2, 3, 1, 0, 2, 3, 1 for the eight repetition TOs. In an example, a base station may implement a similar procedure for multiple repetition TOs of a downlink transport block. A wireless device may decode multiple repetition TOs received from the base station.

In NR, two types of multi-antenna precoding are supported for uplink transmission of transport block(s): codebook-based transmission and non-codebook-based transmission. Both types of multi-antenna precoding may be used together with multiple repetition TOs, where a transport block may be precoded and transmitted multiple times in respective repetition TOs. The precoded transport blocks may be mapped to a same uplink spatial domain transmission filter before each repetition transmission. A spatial domain transmission filter may correspond to a particular transmit and/or receive beam by forming a particular transmit and/or receive beam. For example, a spatial domain transmission filter may map M antenna ports to N physical antennas using a transformation (where M is greater than or equal to one and is less than or equal to N). The transformation may be a linear transformation. In an example, a particular transmit and/or receive beam may apply different amplitude and/or phase shifts to different antenna elements (e.g. physical antennas). In an example, a particular transmit and/or receive beam may generate to a particular signal transmission based on an antenna pattern.

FIG. 18 illustrates an example of beam management for codebook-based uplink transmission with multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure. As shown in FIG. 18, the uplink transmission is performed between a wireless device and a base station. In codebook-based uplink transmission, the base station may determine a suitable uplink transmission rank (or number of layers to be transmitted) and a corresponding precoder matrix to be used for the uplink transmission. To determine the suitable uplink transmission rank and the corresponding precoder matrix, the base station may transmit to the wireless device one or more RRC messages comprising configuration parameters. The configuration parameters may indicate an SRS resource set comprising one or more SRS resources. Each of the one or more SRS resources may indicate a multi-port SRS that is mapped to a set of antenna ports of the wireless device via an uplink spatial domain transmission filter. The base station may perform measurements on the one or more SRS resources to estimate the channels between antenna ports of the wireless device (corresponding to the at least one of the one more SRS resources) and the receive antennas of the base station. Based on the measurements of the one or more SRS resources, the base station may determine the suitable uplink transmission rank and the corresponding precoder matrix. The base station may select the corresponding precoder matrix from an uplink codebook. The uplink codebook may comprise a number of antenna ports being equal to the number of antenna ports of the one of the one or more SRS resources. The number of antenna ports of the one or more SRS resources may be configured by a higher layer parameter (e.g., an RRC parameter nrofSRS-Ports in SRS-Config).

The base station may transmit a downlink control information (DCI) comprising: an uplink scheduling grant for the uplink transmission and an indication of the uplink transmission rank, the precoder matrix, and the indication of at least one of the one more SRS resources used by the base station to determine the precoder matrix and uplink transmission rank. For example, the DCI may comprise a transmitted precoding matrix indicator (TPMI) that indicates the precoder matrix, a rank indicator (RI) that indicates the transmission rank, and a SRS resource indicator (SRI) that indicates the at least one of the one more SRS resources used to determine the precoder matrix, uplink spatial domain transmission filter and uplink transmission rank. The DCI may be sent to the wireless device via DCI format 0_0 or DCI format 0_1 of a PDCCH. The wireless device applies the precoder matrix and the uplink spatial domain transmission filter determined based on the DCI to one or more transport blocks for transmission via a PUSCH scheduling by the DCI. Different SRS resources may be transmitted using different spatial domain transmission filters during a beam sweeping procedure. The output of the precoding may be applied to the uplink spatial domain transmission filter used to transmit the SRS indicated by the SRI before the one or more transport blocks are transmitted. The uplink spatial domain filter may correspond to a particular uplink beam (or a particular spatial domain) as shown in FIG. 18. The same precoder and the same spatial domain transmission filter may be used for each repetition transmission occasion (TO) of the one or more transport blocks as shown in FIG. 18. The wireless device may transmit each TO of the one or more transport blocks with a same uplink transmission power (e.g., with same uplink transmission power parameters comprising P0-PUSCH-AlphaSet, path loss reference signal, and/or closed loop index for power control when the wireless device performing an uplink power control). For example, the wireless device may transmit TO0, TO1, TO2, and TO3 respectively with the same uplink transmission power as shown in FIG. 18.

FIG. 19 illustrates an example of beam management for non-codebook-based uplink transmission with multiple repetition transmission occasions as per an aspect of an embodiment of the present disclosure. As shown in FIG. 19, the uplink transmission is performed between a wireless device and a base station. For non-codebook-based transmission, base station may schedule one or more transport blocks with multiple repetition TOs from a wireless device via DCI format 0_1 (or DCI format 0_0) of PDCCH. The wireless device may determine a PUSCH precoder and transmission rank (e.g., for the transport block with multiple repetition TOs) based on an SRI of the PDCCH in response to multiple SRS resources being configured by the base station to the wireless device (e.g., via an RRC message). The SRI may be given by an SRS resource indicator of DCI in the PDCCH. The wireless device may use one or more SRS resources for an SRS transmission. In an example, a maximum number of SRS resources configured by the base station to the wireless device for simultaneous transmission in a same symbol may be determined based on a UE capability. A maximum number of SRS resources in an SRS resource set may be determined based on the UE capability. The SRS resources transmitted simultaneously by the wireless device may occupy same RBs. In an example, the base station may configure one SRS port for each SRS resource to the wireless device. The base station may configure one SRS resource set to the wireless device via higher layer (e.g., RRC layer) parameter usage in SRS-ResourceSet set to ‘nonCodebook’. In an example, a maximum number of SRS resources configured for non-codebook-based uplink transmission may be 4, 6, 8, 10, 12, 14, or 16. An indicated SRI in slot n may be associated with a most recent transmission of SRS resource(s) identified by the SRI. The SRS transmission indicated by the SRI may be prior to a PDCCH carrying the SRI, for example, the SRS transmission may be a most recent transmission prior to the PDCCH. For non-codebook-based transmission, the wireless device may calculate a precoder used for a transmission of SRS based on a measurement of an associated non-zero power (NZP) CSI-RS resource. The wireless device may be configured by the base station (e.g., via an RRC message) with one NZP CSI-RS resource for the SRS resource set with higher layer (e.g., RRC layer) parameter usage in SRS-ResourceSet set to ‘nonCodebook’. The wireless device may perform a one-to-one mapping from the indicated SRI(s) to the indicated DM-RS ports(s) and corresponding PUSCH layers given by DCI format 0_1 of the PDCCH. The wireless device may transmit the transport block with multiple repetition TOs using same antenna ports as the SRS port(s) in the SRS resource(s) indicated by SRI(s) given by DCI format 0_1 of the PDCCH. For non-codebook-based uplink transmission, the wireless device may not expect to be configured by the base station (e.g., via an RRC message) with both spatialRelationInfo for SRS resource and associatedCSI-RS in SRS-ResourceSet for the SRS resource set.

For non-codebook-based transmission, the wireless device may be scheduled by the base station with DCI format 0_1 of the PDCCH in response to at least one SRS resource being configured in SRS-ResourceSet with usage set to ‘nonCodebook’. The wireless device may transmit the transport blocks (e.g., with multiple repetition TOs) with a same uplink spatial domain transmission filter used for a transmission of the SRS resource(s) indicated by the SRI of the DCI (e.g., DCI format 0_1) in the PDCCH. Because SRS resources are typically transmitted at different time using different spatial domain transmission filters during a beam sweeping procedure, the output of the precoding (e.g., the precoding may be based on a UE implementation) may be applied to the uplink spatial domain transmission filter used to transmit the SRS indicated by the SRI before the one or more transport blocks are transmitted. The uplink spatial domain filter may correspond to a particular uplink beam (or a particular spatial domain) as shown in FIG. 19. The same precoder (e.g., the precoder may be based on the UE implementation) and/or the same spatial domain transmission filter are used for each repetition transmission occasion (TO) of the one or more transport blocks as further shown in FIG. 19. The wireless device may transmit each TO of the one or more transport blocks with a same uplink transmission power (e.g., with same uplink transmission power parameters comprising P0-PUSCH-AlphaSet, path loss reference signal, and/or closed loop index for power control when the wireless device performing an uplink power control). For example, the wireless device may transmit TO0, TO1, TO2, and TO3 respectively with the same uplink transmission power as shown in FIG. 19.

In an example, the wireless device may be configured by the base station with higher layer (e.g., RRC layer) parameter spatialRelationInfo containing an ID of a reference SS/PBCH block (SSB). The wireless device may transmit a target SRS resource with a same spatial domain transmission filter used for a reception of the reference SSB, for example, based on beam correspondence capability of the wireless device. In an example, the wireless device may be configured by the base station with the higher layer (e.g., RRC layer) parameter spatialRelationInfo containing the ID of a reference CSI-RS. The wireless device may transmit the target SRS resource with a same spatial domain transmission filter used for a reception of the reference periodic CSI-RS (or of a reference semi-persistent CSI-RS), for example, based on beam correspondence capability of the wireless device. In an example, the wireless device may be configured by the base station with higher layer (e.g., RRC layer) parameter spatialRelationInfo containing the ID of a reference SRS. The wireless device may transmit the target SRS resource with a same spatial domain transmission filter used for a transmission of the reference SRS.

As mentioned, and shown in FIG. 18 and FIG. 19, in existing codebook-based and non-codebook-based uplink transmissions with multiple repetition TOs, a precoded transport block may be applied to a same spatial domain transmission filter and a same uplink transmission power for each repetition TO. The base station may indicate a transmission power command (TPC) for the multiple repetition TOs to the wireless device via the TPC indicator in the scheduling DCI. Because the transport block is applied to the same uplink transmission power for each repetition TO using a codebook-based and/or a non-codebook-based precoding, the full potential of repetition transmission to increase reliability may not be realized. Additional reliability may be realized through power control enhancement by using two or more different uplink transmission powers for the multiple repetition TOs (e.g., based on different redundancy versions, and/or different panels/TRPs associated with different TOs). One approach to vary the uplink transmission powers over the different repetition TOs may be to extend the TPC in the scheduling DCI by changing the DCI format and increasing the DCI's overall size to indicate more uplink transmission powers for the multiple repetition TOs. However, the signaling overhead of the physical layer and power consumption and detection complexity of the wireless device may be significantly increased with the increase in size of the DCI format.

Example embodiments implement enhanced control signaling between a base station and a wireless device to enable power control enhancement for the multiple repetition TOs. Example embodiments describe procedures for the base station and the wireless device to determine different uplink transmission powers for different repetition TOs implementing power control enhancement. Example embodiments of the present disclosure are directed to an approach for increasing the reliability of uplink transmission of a transport block transmitted over multiple repetition TOs. Example embodiments of the present disclosure increase the reliability of uplink transmission of a transport block transmitted over multiple repetition TOs without indicating an individual TPC for each of the multiple repetition TOs in the DCI used to schedule the transport block for the uplink transmission.

Example embodiments of the present disclosure determine one or more additional uplink transmission powers for transmitting a transport block over multiple repetition TOs. Example embodiments of the present disclosure determine the one or more additional uplink transmission powers using one or more redundancy versions (RVs) and/or using one or more TCI states indicated in the DCI scheduling the uplink transmission of the transport block. Example embodiments of the present disclosure determine the one or more additional uplink transmission powers based on RRC layer enhancement and/or MAC layer enhancement (e.g., with new RRC message(s) and/or new MAC CE(s)). Embodiments of the present disclosure may be used for one or more types of transmissions with multiple repetition TOs, including both codebook-based and non-codebook-based transmission with multiple repetition TOs.

The base station may transmit, to a wireless device, RRC message(s) comprising configuration parameter(s) of one or more SRS resource sets. Each of the one or more SRS resource sets may comprise one or more SRS resources (e.g., SRS resource 0, SRS resource 1, SRS resource 2, and SRS resource 3). For example, the base station may transmit to the wireless device RRC message(s) comprising an SRS-Config information element. The SRS-Config information element may be used to configure SRS transmissions (e.g., resource type, usage, pathloss reference RS, spatial relation information, resource mapping, transmission comb, associated CSI-RS, and/or the like). The SRS-Config information element may indicate one or more SRS resources and/or one or more SRS resource sets to the wireless device. The base station may indicate the wireless device to transmit at least one of three types of SRS: periodic SRS transmission, aperiodic SRS transmission, and semi-persistent (SP) SRS transmission. In an example, for the periodic SRS transmission, slots in which SRSs may be transmitted may be indicated by the base station via cell-specific broadcast signaling, and/or UE-specific signaling (e.g., comprising the SRS-Config information element). In an example, periodicity of the periodic SRS transmission may be a value from as often as once every 2 ms to as infrequently as once every 160 ms. The wireless device may transmit SRSs in SC-FDMA or OFDM symbols in the configured slots. In an example, the wireless device may transmit aperiodic SRS in response to receiving a DCI indicating the aperiodic SRS transmission. A codepoint of the DCI may trigger one or more SRS resource sets configured by the SRS-Config information element. The SRS request field in the DCI (e.g., DCI format 0_1 and DCI format 1_1) may indicate the triggered SRS resource set(s). In an example, the wireless device may receive configuration parameters of SP SRS transmission (e.g., the SRS-Config information element) from the base station. The configuration parameters may comprise at least one of: a periodicity of the SP SRS transmission, a time/frequency radio resource, cyclic shift parameters, and/or other radio parameters (e.g., bandwidth, frequency hopping, transmission comb and offset, frequency-domain position). The wireless device may transmit the SP SRS in response to receiving a first MAC CE activating the SP SRS. The wireless device may repeat the SP SRS transmission with the periodicity until receiving a second MAC CE deactivating the SP SRS. The wireless device may deactivate the SP SRS and stop the SP SRS transmission in response to receiving the second MAC CE deactivating the SP SRS.

FIG. 20 illustrates an example of uplink transmission with multiple repetition transmission occasions and multiple redundancy versions as per an aspect of an embodiment of the present disclosure. As shown in FIG. 20, the uplink transmission is performed from a wireless device to a base station. The wireless device may transmit one or more SRS transmissions with uplink spatial domain transmission filter(s) (or uplink beam(s)) to the base station. The wireless device may transmit a transport block to the base station via a PUSCH with multiple repetition TOs (e.g., repetition TO0, TO1, TO2, and TO3 scheduled by DCI format 0_0 or DCI format 0_1 in a PDCCH). The base station may transmit a DCI indicating a RV sequence to the wireless device. Each of the multiple repetition TOs may be associated with a RV of the RV sequence (e.g., TO0 may be associated with RV0, TO1 may be associated with RV2, TO2 may be associated with RV3, TO3 may be associated with RV1). In an example, the base station may configure the multiple repetition TOs to the wireless device via RRC message(s). In an example, the base station may indicate the multiple repetition TOs to the wireless device via a DCI. In an example, the base station may indicate the multiple repetition TOs to the wireless device via a MAC CE. In an example, the base station may configure multiple numbers of repetition TOs to the wireless device via RRC message(s). The base station may indicate one of the multiple numbers of repetition TOs to the wireless device via a DCI and/or a MAC CE. The wireless device may determine a first uplink transmission power for a first portion of the PUSCH with multiple repetition TOs. The wireless device may determine a second uplink transmission power for a second portion of the PUSCH with multiple repetition TOs. The wireless device may transmit the first portion of the multiple repetition TOs with the first uplink transmission power. The wireless device may transmit the second portion of the multiple repetition TOs with the second uplink transmission power. In an example, the first portion and the second portion may be associated with different RVs. For example, the first portion may comprise repetition transmission occasion 0 (TO0) and repetition transmission occasion 2 (TO2) (e.g., the multiple repetition TOs comprising 4 repetition TOs). In an example, the first portion may be associated with RV0 and RV3. The second portion may comprise repetition transmission occasion 1 (TO1) and repetition transmission occasion 3 (TO3) (e.g., the multiple repetition TOs comprising 4 repetition TOs). In an example, the second portion may be associated with RV2 and RV1.

In an example, the first portion may be a first half of the multiple repetition TOs. The second portion may be a second half of the multiple repetition TOs. For example, the first portion may comprise repetition TO0 and repetition TO1 and the second portion may comprise repetition TO2 and repetition TO3 in response to the multiple repetition TOs comprising 4 repetition TOs (e.g., repetition TO0, repetition TO1, repetition TO2, and repetition TO3). The wireless device may determine the first uplink transmission power for the first portion of the PUSCH with multiple repetition TOs. In an example, the wireless device may determine the first uplink transmission power based on first power control parameters for the uplink transmission. The wireless device may determine the second uplink transmission power for the second portion of the PUSCH with multiple repetition TOs. In an example, the wireless device may determine the second uplink transmission power based on second power control parameters for the uplink transmission. The wireless device may transmit the first portion of the PUSCH (with multiple repetition TOs) with the first uplink transmission power. The wireless device may transmit the second portion of the PUSCH (with multiple repetition TOs) with the second uplink transmission power. The wireless device may determine the first uplink transmission power and/or the second uplink transmission power according to the descriptions as in FIG. 21A, FIG. 21B, FIG. 21C, and FIG. 21D.

FIG. 21A illustrates an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure. A base station may transmit an RRC message comprising configuration parameters to a wireless device. In an example, the configuration parameters may indicate a power offset value. The base station may transmit a PDCCH comprising a DCI to the wireless device. In an example, the DCI scheduling a PUSCH with multiple repetition TOs may indicate an RV sequence (e.g., RV0, RV2, RV3, and RV1). The DCI may comprise a TPC command for uplink transmission power control. In an example, the wireless device may determine one or more uplink transmission powers based on the RV sequence. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the TPC. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the power offset value. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence, the power offset value, and the TPC. The wireless device may determine a first uplink transmission power for a first portion of the multiple repetition TOs. The wireless device may determine a second uplink transmission power for a second portion of the multiple repetition TOs. The first portion may comprise repetition TOs with RV0 and/or RV3 of the multiple repetition TOs. The second portion may comprise repetition TOs with RV1 and/or RV2 of the multiple repetition TOs. In an example, the wireless device may determine the first uplink transmission power for the first portion of the multiple repetition TOs based on the power offset value and the TPC. For example, the first uplink transmission power may be P0 plus the power offset value. In an example, the wireless device may determine the second uplink transmission power for the second portion of the multiple repetition TOs based on the TPC. For example, the second uplink transmission power may be P0. In an example, the wireless device may determine the P0 based on an uplink power control for physical uplink shared channel, for example, P0=

$\left. {{P_{{PUSCH},b,f,c}\left( {i,j,q_{d},l} \right)} = {\min\begin{Bmatrix} {{{P_{{CMAX},f,c}(i)},}\mspace{745mu}} \\ {{P_{{O\_{PUSCH}},b,f,c}(j)} + {10\mspace{14mu}{\log_{10}\left( {2^{\mu} \cdot {M_{{RB},b,f,c}^{PUSCH}(i)}} \right)}} + {{\alpha_{b,f,c}(j)} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + {\Delta_{{TF},b,f,c}(i)} +} \\ {f_{b,f,c}\left( {i,l} \right)} \end{Bmatrix}\mspace{14mu}{dBm}}} \right\rbrack.$

In an example, P_(CMAX,f,c)(i) may be the UE configured maximum output power for carrier f of serving cell c in PUSCH transmission occasion i. In an example, P_(O_PUSCH,b,f,c)(j) may be a parameter composed of a sum of a component P_(O_NOMINAL_PUSCH,f,c)(j) and a component P_(O_UE_PUSCH,b,f,c)(j) where j∈{0, 1, . . . , J−1}. In an example, M_(RB,b,f,c) ^(PUSCH)(i) may be a bandwidth of the PUSCH resource assignment expressed in number of resource blocks for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c and μ is a SCS configuration. In an example, PL_(b,f,c)(q_(d)) may be a downlink pathloss estimate in dB calculated by the UE using reference signal (RS) index q_(d) for the active DL BWP of carrier f of serving cell c. In an example, Δ_(TF,b,f,c)(i)=10 log₁₀ ((2^(BPRE·K) ^(S) −1)·β_(offset) ^(PUSCH)) for K_(S)=1.25 and Δ_(TF,b,f,c)(i)=0 for K_(S)=0 where K_(S) is provided by deltaMCS for each UL BWP b of each carrier f and serving cell c. In an example, f_(b,f,c)(i,l) may be a closed loop power control parameter for the active UL BWP b of each carrier f and each serving cell c base on the TPC in DCI. In an example, α_(b,f,c)(j) may be a pathloss scaling factor for the active UL BWP b of carrier f of serving cell c. In an example, the wireless device may transmit repetition TOs associated with RV0 and/or RV3 with the first uplink transmission power. The wireless device may transmit repetition TOs associated with RV1 and/or RV2 with the second uplink transmission power. In an example, the first uplink transmission power may be greater than the second transmission power by the power offset value.

FIG. 21B illustrates an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure. A base station may transmit a PDCCH comprising a DCI to the wireless device. In an example, the DCI scheduling a PUSCH with multiple repetition TOs may indicate an RV sequence (e.g., RV2, RV3, RV1, and RV0). The DCI may comprise a TPC for uplink transmission power control. In an example, the wireless device may determine one or more uplink transmission powers based on the RV sequence. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the TPC. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the power offset value. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence, the power offset value, and the TPC. The wireless device may determine a first uplink transmission power for a first portion of the multiple repetition TOs. For example, the first uplink transmission power may be P0 plus the power offset value as described in FIG. 21A. The wireless device may determine a second uplink transmission power for a second portion of the multiple repetition TOs. For example, the second uplink transmission power may be P0 as described in FIG. 21A. The first portion may comprise repetition TOs with RV0 and/or RV3 of the multiple repetition TOs. The second portion may comprise repetition TOs with RV1 and/or RV2 of the multiple repetition TOs. In an example, the wireless device may determine the first uplink transmission power for the first portion of the multiple repetition TOs based on the power offset value and the TPC. In an example, the wireless device may determine the second uplink transmission power for the second portion of the multiple repetition TOs based on the TPC. For example, the wireless device may transmit repetition TOs associated with RV0 and/or RV3 with the first uplink transmission power. The wireless device may transmit repetition TOs associated with RV1 and/or RV2 with the second uplink transmission power. In an example, the first uplink transmission power may be greater than the second transmission power by the power offset value.

FIG. 21C illustrates an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure. A base station may transmit a PDCCH comprising a DCI to the wireless device. In an example, the DCI scheduling a PUSCH with multiple repetition TOs may indicate an RV sequence (e.g., RV3, RV1, RV0, and RV2). The DCI may comprise a TPC for uplink transmission power control. In an example, the wireless device may determine one or more uplink transmission powers based on the RV sequence. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the TPC. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the power offset value. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence, the power offset value, and the TPC. The wireless device may determine a first uplink transmission power for a first portion of the multiple repetition TOs. For example, the first uplink transmission power may be P0 plus the power offset value as described in FIG. 21A. The wireless device may determine a second uplink transmission power for a second portion of the multiple repetition TOs. For example, the second uplink transmission power may be P0 as described in FIG. 21A. The first portion may comprise repetition TOs with RV0 and/or RV3 of the multiple repetition TOs. The second portion may comprise repetition TOs with RV1 and/or RV2 of the multiple repetition TOs. In an example, the wireless device may determine the first uplink transmission power for the first portion of the multiple repetition TOs based on the power offset value and the TPC. In an example, the wireless device may determine the second uplink transmission power for the second portion of the multiple repetition TOs based on the TPC. For example, the wireless device may transmit repetition TOs associated with RV0 and/or RV3 with the first uplink transmission power. The wireless device may transmit repetition TOs associated with RV1 and/or RV2 with the second uplink transmission power. In an example, the first uplink transmission power may be greater than the second transmission power by the power offset value.

FIG. 21D illustrates an example of power control with different redundancy versions as per an aspect of an embodiment of the present disclosure. A base station may transmit a PDCCH comprising a DCI to the wireless device. In an example, the DCI scheduling a PUSCH with multiple repetition TOs may indicate an RV sequence (e.g., RV1, RV0, RV2, and RV3). The DCI may comprise a TPC for uplink transmission power control. In an example, the wireless device may determine one or more uplink transmission powers based on the RV sequence. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the TPC. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence and the power offset value. In an example, the wireless device may determine the one or more uplink transmission powers based on the RV sequence, the power offset value, and the TPC. The wireless device may determine a first uplink transmission power for a first portion of the multiple repetition TOs. For example, the first uplink transmission power may be P0 plus the power offset value as described in FIG. 21A. The wireless device may determine a second uplink transmission power for a second portion of the multiple repetition TOs. For example, the second uplink transmission power may be P0 as described in FIG. 21A. The first portion may comprise repetition TOs with RV0 and/or RV3 of the multiple repetition TOs. The second portion may comprise repetition TOs with RV1 and/or RV2 of the multiple repetition TOs. In an example, the wireless device may determine the first uplink transmission power for the first portion of the multiple repetition TOs based on the power offset value and the TPC. In an example, the wireless device may determine the second uplink transmission power for the second portion of the multiple repetition TOs based on the TPC. For example, the wireless device may transmit repetition TOs associated with RV0 and/or RV3 with the first uplink transmission power. The wireless device may transmit repetition TOs associated with RV1 and/or RV2 with the second uplink transmission power. In an example, the first uplink transmission power may be greater than the second transmission power by the power offset value.

FIG. 22 illustrates an example of a power control procedure for uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure. A wireless device may receive one or more RRC messages from a base station (e.g., at time T1). The one or more RRC messages may comprise configuration parameter(s). In an example, the configuration parameter(s) may indicate a plurality of repetition TOs for a transport block (TB). In an example, the configuration parameter(s) may indicate a power offset value. The wireless device may receive a PDCCH comprising a DCI from the base station (e.g., at time T2). The DCI may indicate a TPC, and/or an RV sequence. Each of the plurality of repetition TOs may be associated with an RV of the RV sequence. In an example, the configuration parameter(s) may indicate a plurality of power offset values. The DCI may indicate a power offset value of the plurality of power offset values. In an example, the configuration parameter(s) may indicate multiple numbers of repetition TOs. The DCI may indicate one of the multiple numbers of repetition TOs. The one of the multiple numbers of repletion TOs may comprise the plurality of repetition TOs. In an example, the wireless device may determine one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence). In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence), and/or the TPC. In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence), and/or the power offset value. In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the TPC, the RV sequence (or an RV of the RV sequence), and/or the power offset value (e.g., at time T3). The determination of the one or more uplink transmission powers may comprise determining a first uplink transmission power for a first portion of the plurality of repetition TOs. The determination of the one or more uplink transmission powers may comprise determining a second uplink transmission power for a second portion of the plurality of repetition TOs. The determinations of the first uplink transmission power for the first portion and the second uplink transmission power for the second portion are described as in FIG. 21A, FIG. 21B, FIG. 21C, and FIG. 21D in response to the DCI indicating different RV sequences. The wireless device may transmit the TB (with the plurality of repetition TOs) via a PUSCH with the one or more uplink transmission powers (e.g., at time T4). The wireless device may transmit the first portion of the plurality of repetition TOs via the PUSCH with the first uplink transmission power. The wireless device may transmit the second portion of the plurality of repetition TOs via the PUSCH with the second uplink transmission power.

FIG. 23 illustrates an example of a power control procedure for uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure. A wireless device may receive one or more RRC messages from a base station (e.g., at time T1). The one or more RRC messages may comprise configuration parameter(s). In an example, the configuration parameter(s) may indicate a plurality of repetition TOs for a transport block (TB). In an example, the configuration parameter(s) may indicate a plurality of power offset values. The wireless device may receive a MAC CE from the base station (e.g., at time T2). The MACE CE may select (or activate) one of the plurality of power offset values for the wireless device. The wireless device may receive a PDCCH comprising a DCI from the base station (e.g., at time T3). The DCI may indicate a TPC, and/or an RV sequence. Each of the plurality of repetition TOs may be associated with an RV of the RV sequence. In an example, the configuration parameter(s) may indicate multiple numbers of repetition TOs. The DCI may indicate one of the multiple numbers of repetition TOs. The one of the multiple numbers of repletion TOs may comprise the plurality of repetition TOs. In an example, the wireless device may determine one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence). In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence), and/or the TPC. In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the RV sequence (or an RV of the RV sequence), and/or the one of the plurality of power offset values. In an example, the wireless device may determine the one or more uplink transmission powers for the plurality of repetition TOs based on the TPC, the RV sequence (or an RV of the RV sequence), and/or the one of the plurality of power offset values (e.g., at time T4). The determination of the one or more uplink transmission powers may comprise determining a first uplink transmission power for a first portion of the plurality of repetition TOs. The determination of the one or more uplink transmission powers may comprise determining a second uplink transmission power for a second portion of the plurality of repetition TOs. The determinations of the first uplink transmission power for the first portion and the second uplink transmission power for the second portion are described as in FIG. 21A, FIG. 21B, FIG. 21C, and FIG. 21D in response to the DCI indicating different RV sequences. The wireless device may transmit the TB (with the plurality of repetition TOs) via a PUSCH with the one or more uplink transmission powers (e.g., at time T5). The wireless device may transmit the first portion of the plurality of repetition TOs via the PUSCH with the first uplink transmission power. The wireless device may transmit the second portion of the plurality of repetition TOs via the PUSCH with the second uplink transmission power.

FIG. 24A illustrates an example of a MAC CE for power offset value selection as per an aspect of an embodiment of the present disclosure. The MAC CE may activate/deactivate (or select/unselect) a plurality of power offset values configured by a base station via an RRC message. The wireless device may determine a power offset value based on an indication of the MAC CE. In an example, the MAC CE may comprise two octets. In an example, the MAC CE may comprise serving cell ID indication. In an example, the MAC CE may comprise BWP ID indication. The MAC CE may activate/deactivate (or select/unselect) the plurality of power offset values on a cell with the serving cell ID. In an example, the MAC CE may activate/deactivate (or select/unselect) the plurality of power offset values on a BWP with the BWP ID. In an example, the MAC CE may activate/deactivate (or select/unselect) the plurality of power offset values on a BWP of a cell with the BWP ID and the serving cell ID. In an example, one bit of the MAC CE may associate with one of the plurality of power offset values configured by the base station via the RRC message (e.g., bi associates with one of the plurality of power offset values, and i is from 0 to 7). In an example, a bi may indicate an activated/deactivated (or selected/unselected) status of one of the plurality of power offset values. In an example, when bi is set to “1”, a power offset value associated with bi may be set activated status (or selected status). In an example, when bi is set to “0”, the power offset value associated with bi may be set deactivated status (or unselected status). In an example, eight bits (e.g., b0, b1, b2, b3, . . . , b7) of the MAC CE may activate (or select) one of the plurality of power offset values (e.g., a total number of the plurality of power offset values is equal to or less than 64). In an example, the eight bits (b0, b1, b2, b3, . . . , b7) may deactivate (or unselect) one of the plurality of power offset values. In an example, the eight bits with values “00000000” may activate (or select) a power offset value with a first index of the plurality of power offset values configured by the base station via the RRC message. In an example, the eight bits with values “00000001” may deactivate (or select) a power offset value with a second index of the plurality of power offset values configured by the base station via the RRC message. The MAC CE may be identified by a MAC PDU sub-header with an LCID. In an example, the LCID may be set to “101101”.

FIG. 24B illustrates an example of a flow chart of power control for an uplink transmission with multiple repetition transmission occasions and redundancy versions as per an aspect of an embodiment of the present disclosure. A wireless device may receive one or more RRC messages from a base station. The one or more RRC messages may comprise configuration parameter(s). The configuration parameter(s) may indicate a plurality of repetition TOs for a transport block (TB). The configuration parameter(s) may indicate one or more power offset values. The wireless device may receive a downlink control information (DCI) indicating a TPC, and/or an RV sequence. The wireless device may determine one or more uplink transmission powers based on the TPC, the RV sequence, and/or a power offset value. The determinations of the one or more uplink transmission powers are described as in FIG. 21A, FIG. 21B, FIG. 21C, and FIG. 21D. The power offset value may be one of the one or more power offset values. The wireless device may transmit the plurality of the repetition TOs for the TB with the one or more uplink transmission powers via a PUSCH. The wireless device may transmit a first portion of the plurality of the repetition TOs for the TB via the PUSCH with the first uplink transmission power. The wireless device may transmit the second portion of the plurality of the repetition TOs for the TB via the PUSCH with the second uplink transmission power.

A wireless device may receive, from a base station, one or more radio resource control messages comprising configuration parameters. The configuration parameters may indicate a power offset value. The wireless device may receive a downlink control information from the base station. The downlink control information may indicate a redundancy version (RV) sequence. The downlink control information may indicate a plurality of repetition transmission occasions. The wireless device may determine, based on the power offset value and the RV sequence, one or more uplink transmission powers for the plurality of repetition transmission occasions. The wireless device may transmit the plurality of repetition transmission occasions with the one or more uplink transmission powers. The plurality of repetition transmission occasions may be transmitted by the wireless device via a physical uplink shared channel. The RV sequence may comprise one or more redundancy versions. Each of the plurality of repetition transmission occasions may be associated with a RV of the RV sequence. The wireless device may determine a RV for a repetition transmission occasion of the plurality of repetition transmission occasions based on the RV sequence and an index of the transmission occasion. The one or more uplink transmission powers may be used by the wireless device for transmissions of the plurality of repetition transmission occasions. The determining, based on the power offset value and the RV sequence, one or more uplink transmission powers for the plurality of repetition transmission occasions may comprise determining an uplink transmission power for each of the plurality of repetition transmission occasions based on the power offset value and the RV sequence.

The determining the uplink transmission power for each of the plurality of repetition transmission occasions based on the power offset value and the RV sequence may comprise determining the uplink transmission power with the power offset value for repetition transmission occasions with systematic bits of the RV sequence. The determining the uplink transmission power with the power offset value for repetition transmission occasions with systematic bits of the RV sequence may comprise determining the uplink transmission power based on the power offset value and a transmission power control command (TPC) for repetition transmission occasions with systematic bits of the RV sequence. The determining the uplink transmission power for each of the plurality of repetition transmission occasions based on the power offset value and the RV sequence may comprise determining the uplink transmission power without the power offset value for repetition transmission occasions without systematic bits of the RV sequence. The determining the uplink transmission power without the power offset value for repetition transmission occasions without systematic bits of the RV sequence may comprise determining the uplink transmission power based on a transmission power control command (TPC) for repetition transmission occasions without systematic bits of the RV sequence. The transmitting the plurality of repetition transmission occasions with the one or more uplink transmission powers may comprise transmitting each of the plurality of repetition transmission occasions with one of the one or more uplink transmission powers. Each of the one or more uplink transmission powers may comprise a different uplink transmission power for transmission.

A wireless device may receive, from a base station, one or more radio resource control messages comprising configuration parameters. The configuration parameters may indicate: a plurality of repetition transmission occasions, and/or a plurality of power offset values. The wireless device may receive a media access control control element (MAC CE) selecting one of the plurality of power offset values. The wireless device may receive a downlink control information indicating a redundancy version (RV) sequence. The wireless device may determine, based on the one of the plurality of power offset values and/or the RV sequence, one or more uplink transmission powers for the plurality of repetition transmission occasions. The wireless device may transmit the plurality of repetition transmission occasions with the one or more uplink transmission powers.

A wireless device may receive, from a base station, one or more radio resource control messages comprising configuration parameters. The configuration parameters may indicate: a plurality of repetition transmission occasions, and/or a plurality of power offset values. The wireless device may receive a downlink control information indicating a redundancy version (RV) sequence and/or one of the plurality of power offset values. The wireless device may determine, based on the RV sequence and/or the one of the plurality of power offset values, one or more uplink transmission powers for the plurality of repetition transmission occasions. The wireless device may transmit the plurality of repetition transmission occasions with the one or more uplink transmission powers.

FIG. 25 illustrates an example of an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure. A wireless device may transmit multiple repetition TOs of a transport block to multiple TRPs. In an example, as shown in FIG. 25, the multiple repetition TOs may comprise 4 repetition TOs (e.g., TO0, TO1, TO2, and TO3) of the transport block. The multiple TRPs may comprise 2 TRPs (e.g., TRP0 and TRP1). In an example, the wireless device may cyclically transmit the multiple repetition TOs to the multiple TRPs. For example, the wireless device may transmit TO0 and TO2 of the 4 repetition TOs to TRP0. The wireless device may transmit TO1 and TO3 of the 4 repetition TOs to TRP1. In an example, the wireless device may sequentially transmit the multiple repetition TOs to the multiple TRPs. For example, the wireless device may transmit TO0 and TO1 of the 4 repetition TOs to TRP0. The wireless device may transmit TO2 and TO3 of the 4 repetition TOs to TRP1. The wireless device may transmit the multiple repetition TOs to different TRPs with different uplink transmission powers. The wireless device may determine the different uplink transmission powers based on different uplink power control parameters. The different uplink power control parameters may comprise different P0-PUSCH-AlphaSets, different path loss reference signals, different power offset values, different TPCs, and/or different closed loop indexes for power control. A base station may transmit a PDCCH (e.g., via TPR0 and/or TRP1) to the wireless device. The PDCCH may comprise one or more transmission configuration indications (TCIs). In an example, the one or more TCIs may comprise TCI0 and TCI1. Each of the one or more TCIs may be associated with a TRP. For example, TCI0 may be associated with TRP0. TCI1 may be associated with TRP1. The wireless device may determine two uplink spatial domain transmission filters based on the one or more TCIs (e.g., TCI0 and TCI1). For example, the wireless device may determine a first uplink spatial domain transmission filter for TRP0 based on TCI0. The wireless device may determine a second uplink spatial domain transmission filter for TRP1 based on TCI1. In an example, the wireless device may transmit first repetition TOs of the multiple repetition TOs to TRP0 with the first uplink spatial domain transmission filter of the two uplink spatial domain transmission filters. The wireless device may transmit second repetition TOs of the multiple repetition TOs to TRP1 with the second uplink spatial domain transmission filter of the two uplink spatial domain transmission filters. In an example, the one or more TCIs may comprise one or more downlink TCIs, or one or more uplink TCIs. Each of the one or more TCIs may be associated with an SRS, a SSB, and/or a CSI-RS. Each of the two uplink spatial domain transmission filters may be associated with an uplink beam. In an example, the wireless device may transmit the first repetition TOs (e.g., TO0 and TO2) of the multiple repetition TOs to TRP0 with a first beam (or the first uplink spatial domain transmission filter). The wireless device may transmit the second repetition TOs (e.g., TO1 and TO3) of the multiple repetition TOs to TRP1 with a second beam (or the second uplink spatial domain transmission filter). The first uplink spatial domain transmission filter may be associated with the first beam. The second uplink spatial domain transmission filter may be associated with the second beam. The wireless device may determine the different uplink transmission powers for repetition TOs transmitted to different TRPs based on the different uplink power control parameters.

FIG. 26 illustrates an example of a power control procedure for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure. A wireless device may receive one or more RRC messages from a base station (e.g., at time T1). The one or more RRC messages may comprise configuration parameter(s). The configuration parameter(s) may indicate a plurality of repetition TOs, and/or a plurality of power control parameters. The plurality of power control parameters may comprise a plurality of P0-PUSCH-AlphaSets, a plurality of path loss reference signals, a plurality of power offset values, and/or a plurality of closed loop indexes for power control. In an example, the configuration parameter(s) may indicate multiple numbers of repetition TOs of a transport block. The base station may transmit a DCI and/or a MAC CE indicating one of the multiple numbers of repetition TOs of the transport block to the wireless device. The one of the multiple numbers of repetition TOs of the transport block may comprise the plurality of repetition TOs of the transport block. In an example, the configuration parameter(s) may indicate a plurality of TCIs. In an example, the configuration parameter(s) may indicate an association between TCI(s) (of the plurality of TCIs) and power control parameter(s). The power control parameter(s) may comprise P0-PUSCH-AlphaSet(s), path loss reference signal(s), power offset value(s), and/or closed loop index(es) for power control. Each of the plurality of TCIs may be associated with one or more power control parameters of the power control parameter(s). The one or more power control parameters may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control.

The wireless device may receive, from the base station, a DCI indicating one or more TPCs, and/or power control parameter(s) (e.g., at time T2). The DCI may indicate the one of the multiple numbers of repetition TOs of the transport block. The power control parameter(s) may be one or more power control parameters of the plurality power control parameters. The DCI indicating the power control parameter(s) may comprise the DCI indicating one or more TCIs. Each of the one or more TCIs may be associated with one or more power control parameters. The association may comprise a configuration of TCI(s) by the base station via RRC message(s) comprises the one or more power control parameters. The one or more power control parameters may be the power control parameter(s). The one or more power control parameters may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control. In an example, each of the one or more TCIs may be associated with a power offset value. Each of the one or more TCIs may be associated with a different power offset value. For example, TCI0 may be associated with power offset value_0. TCI1 may be associated with power offset value_1. Power offset value_0 may be different from power offset value_1. In an example, the DCI may comprise one or more bitfields. The one or more bitfields may indicate the power control parameter(s). For example, the one or more bitfields may indicate power offset value_0 for TRP0. The one or more bitfields may indicate power offset value_1 for TRP1.

The wireless device may determine one or more uplink transmission powers based on the one or more TPCs, and/or the association between the one or more TCIs and the power control parameter(s) (e.g., at time T3). The wireless device may determine the one or more uplink transmission powers based on one or more power offset values associated with the one or more TCIs indicated by the DCI. For example, the wireless device may determine P0 for TRP0 based on power control parameters as described in FIG. 21A. The wireless device may determine P0 for TRP1 based on power control parameters as described in FIG. 21A. The wireless device may determine the one or more uplink transmission powers based on the one or more TPCs, and/or the power control parameter(s) indicated by the DCI. In an example, the one or more TCIs may comprise TCI0 and TCI1. The TCI0 may be associated with a first power control parameter. The first power control parameter may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control. The TCI1 may be associated with a second power control parameter. The second power control parameter may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control. In an example, the first power control parameter may be power offset value_0. The second power control parameter may be power offset value_1. The wireless device may determine a first uplink transmission power based on the first power control parameter. In an example, the wireless device may determine the first uplink transmission power as P0 plus the power offset value_0. The wireless device may determine a second uplink transmission power based on the second power control parameter. In an example, the wireless device may determine the second uplink transmission power as P0 plus the power offset value_1. The wireless device may transmit the multiple repetition TOs of the transport block with the one or more uplink transmission powers to the multiple TRPs (e.g., at time T4). In an example, the wireless device may transmit TO0 and TO2 with the first uplink transmission power to TPR0 (e.g., in response to cyclical transmission being configured by the base station via RRC message(s)). The wireless device may transmit TO1 and TO3 with the second uplink transmission power to TPR1 (e.g., in response to cyclical transmission being configured by the base station via RRC message(s)). In an example, the wireless device may transmit TO0 and TO1 with the first uplink transmission power to TPR0 (e.g., in response to sequential transmission being configured by the base station via RRC message(s)). The wireless device may transmit TO2 and TO3 with the second uplink transmission power to TPR1 (e.g., in response to sequential transmission being configured by the base station via RRC message(s)). In an example, the wireless device may transmit repetition TOs to different TRPs based on RV versions as described in FIG. 21A, FIG. 21B, FIG. 21C, FIG. 21D. For example, the wireless device may transmit repetition TOs to different TRPs with a power of P0 in response to the repetition TOs without systematic bits. The wireless device may transmit repetition TOs to different TRPs with a power of P0 plus a power offset value (e.g., the power offset value may be power offset vlau_0 for TRP0, and the power offset value may be power offset value_1 for TRP1) in response to the repetition TOs with systematic bits (e.g., as described in FIG. 21A, FIG. 21B, FIG. 21C, FIG. 21D). In an example, each of the one or more TCIs may be associated with a panel of the wireless device. The wireless device may comprise two panels (e.g., panel_0 and panel_1). For example, TCI0 may be associated with panel_0 of the wireless device. TCI1 may be associated with panel_1 of the wireless device. The first power control parameter may be associated with panel_0 (e.g., based on panel_0 associated with TCI0 indicated by the DCI), for example, power offset value_0 may be associated with panel_0 of the wireless device. The second power control parameter may be associated with panel_1 (e.g., based on panel_1 associated with TCI1 indicated by the DCI), for example, power offset value_1 may be associated with panel_1 of the wireless device. The wireless device may transmit repetition TOs with the first uplink transmission power via panel_0 to TRP0. The wireless device may transmit repetition TOs with the second uplink transmission power via panel_1 to TRP1.

FIG. 27A illustrates an example of power control parameter indication for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure. A base station may transmit a PDCCH comprising a DCI to a wireless device. The DCI may comprise a bitfield indicating one or more uplink power control parameters for multiple TRPs. The one or more power control parameters may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control. The wireless device may determine uplink transmission power(s) based on the one or more uplink power control parameters. The wireless device may transmit repetition TOs with the uplink transmission power(s) to the multiple TRPs as described in FIG. 26. In an example, the bitfield may comprise two bits. The bitfield may indicate power control parameter 0 for TRP0 and power control parameter 3 for TRP1 in response to the bitfield being equal to 00. The bitfield may indicate power control parameter 1 for TRP0 and power control parameter 2 for TRP1 in response to the bitfield being equal to 01. The bitfield may indicate power control parameter 2 for TRP0 and power control parameter 1 for TRP1 in response to the bitfield being equal to 10. The bitfield may indicate power control parameter 3 for TRP0 and power control parameter 0 for TRP1 in response to the bitfield being equal to 11. The power control parameter (e.g., parameter 0, parameter 1, parameter 2, or parameter 3) may comprise a P0-PUSCH-AlphaSets, a path loss reference signal, a power offset value, and/or a closed loop index for power control. The wireless device may determine uplink transmission power(s) for the multiple TRPs based on the power control parameter(s) indicated by the DCI with the bitfield as described in FIG. 26.

FIG. 27B illustrates an example of power control parameter indication for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure. A base station may transmit a PDCCH comprising a DCI to a wireless device. The DCI may comprise a bitfield indicating one or more TCIs for multiple TRPs. The one or more TCIs may be associated one or more power control parameters. The one or more power control parameters may comprise one or more P0-PUSCH-AlphaSets, one or more path loss reference signals, one or more power offset values, and/or one or more closed loop indexes for power control. The wireless device may determine uplink transmission power(s) based on the one or more power control parameters. The wireless device may transmit repetition TOs with the uplink transmission power(s) to the multiple TRPs as described in FIG. 26. In an example, the bitfield may comprise two bits. The bitfield may indicate TCI0 for TRP0 and TCI2 for TRP1 in response to the bitfield being equal to 00. The bitfield may indicate TCI1 for TRP0 and TCI3 for TRP1 in response to the bitfield being equal to 01. The bitfield may indicate TCI2 for TRP0 and TCI0 for TRP1 in response to the bitfield being equal to 10. The bitfield may indicate TCI3 for TRP0 and TCI1 for TRP1 in response to the bitfield being equal to 11. Each of the multiple TCIs (e.g., TCI0, TCI1, TCI2, TCI3) may be associated with a power control parameter (e.g., configured by the base station via an RRC message). In an example, TCI0 may be associated with power control parameter 0. TCI1 may be associated with power control parameter 1. TCI2 may be associated with power control parameter 2. TCI3 may be associated with power control parameter 3. The power control parameter (e.g., power control parameter 0, power control parameter 1, power control parameter 2, or power control parameter 3) may comprise a P0-PUSCH-AlphaSets, a path loss reference signal, a power offset value, and/or a closed loop index for power control. The wireless device may determine the power control parameter(s) associated with the one or more TCIs indicated by the DCI. The wireless device may determine uplink transmission power(s) for the multiple TRPs based on the power control parameter(s) associated with the multiple TCIs indicated by the DCI with the bitfield as described as FIG. 26. The wireless device may determine uplink transmission power(s) for the multiple TRPs based on the association between power control parameter(s) and the multiple TCIs indicated by the DCI. The wireless device may transmit the multiple repetition TOs to the multiple TRPs with the uplink transmission power(s) as described in FIG. 26.

FIG. 28 illustrates an example of a flow chart of power control for an uplink transmission with multiple repetition transmission occasions and multiple TRPs as per an aspect of an embodiment of the present disclosure. A wireless device may receive one or more RRC messages from a base station. The one or more RRC messages may comprise configuration parameter(s). The configuration parameter(s) may indicate a plurality of repetition TOs, and/or an association between TCI(s) and power control parameter(s). The wireless device may receive a downlink control information (DCI) indicating one or more TPCs, and/or one or more TCIs. The wireless device may determine one or more uplink transmission powers based on the one or more TPCs, and/or the association between the one or more TCIs and power control parameter(s). The wireless device may transmit the multiple repetition TOs of a transport block with the one or more uplink transmission powers to the multiple TRPs.

A wireless device may receive, by a wireless device from a base station, one or more radio resource control messages comprising configuration parameters. The configuration parameters indicate an association between a transmission configuration indication (TCI) status and a power control parameter. The wireless device may receive a downlink control information indicating one or more TCI statuses. The wireless device may determine, based on the one or more TCI statuses and/or the association, one or more uplink transmission powers for a plurality of repetition transmission occasions of a transport block. The wireless device may transmit the plurality of repetition transmission occasions of the transport block with the one or more uplink transmission powers. The power control parameter may comprise at least one of: a pathloss reference signal, a p0 and alpha set, a power offset value, and a closed loop index for power control. Each of the one or more TCI statuses may be associated with one or more power control parameters. Each of the one or more TCI statuses may be associated with one or more reference signals. The one or more reference signals may comprise at least one of: a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), and a sounding reference signal (SRS). The transmitting the plurality of repetition transmission occasions of the transport block with the one or more uplink transmission powers may comprise transmitting each of the plurality of repetition transmission occasions with one of the one or more uplink transmission powers. Each of the one or more uplink transmission powers may comprise a different uplink transmission power for the plurality of repetition transmission occasions. The downlink control information (DCI) may comprise one or more bitfields indicating the one or more TCI statuses. 

What is claimed is:
 1. A method comprising: receiving, by a wireless device, a power offset value associated with a difference between transmission powers of different redundancy versions (RVs) of repetition occasions of a transport block; receiving a downlink control information indicating: a sequence of RVs; and a quantity of the repetition occasions; determining, based on the power offset value and the RVs, a transmission power for one or more repetition occasions of the repetition occasions; and transmitting, with the transmission power, one or more repetitions of the transport block via the one or more repetition occasions.
 2. The method of claim 1, wherein the quantity of the repetition occasions comprises the one or more repetitions and one or more second repetition occasions, and wherein the method further comprises: determining, based on the sequence of RVs, a second transmission power for one or more second repetition occasions of the repetition occasions; and transmitting, with the second transmission power, one or more second repetitions of the transport block via the one or more second repetition occasions.
 3. The method of claim 2, wherein the one or more second repetition occasions correspond to one or more second RVs, of the sequence of RVs, not associated with the power offset value, and wherein the second transmission power is not determined based on the power offset value in response to the one or more second RVs not being associated with the power offset value.
 4. The method of claim 3, wherein the one or more second RVs are not associated with the power offset value in response to the one or more second RVs corresponding to non-systematic bits of the RV sequence.
 5. The method of claim 1, wherein each of the repetition occasions is associated with an RV of the sequence of RVs.
 6. The method of claim 1, further comprising determining an RV, from the sequence of RVs, for each of the repetition occasions based on the sequence of RVs and an index of each of the repetition occasions.
 7. The method of claim 1, wherein the one or more repetition occasions correspond to one or more RVs, of the sequence of RVs, associated with the power offset value, and wherein the transmission power is determined based on the power offset value in response to the one or more RVs being associated with the power offset value.
 8. The method of claim 7, wherein the one or more RVs are associated with the power offset value in response to the one or more RVs corresponding to systematic bits of the RV sequence.
 9. The method of claim 1, wherein a length of the sequence of RVs is equal to or less than the quantity of the repetition occasions.
 10. The method of claim 1, wherein the transmission power is determined to be the same for each of the one or more repetition occasions.
 11. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive a power offset value associated with a difference between transmission powers of different redundancy versions (RVs) of repetition occasions of a transport block; receive a downlink control information indicating: a sequence of RVs; and a quantity of the repetition occasions; determine, based on the power offset value and the RVs, a transmission power for one or more repetition occasions of the repetition occasions; and transmit, with the transmission power, one or more repetitions of the transport block via the one or more repetition occasions.
 12. The wireless device of claim 11, wherein the quantity of the repetition occasions comprises the one or more repetitions and one or more second repetition occasions, and wherein the instructions further cause the wireless device to: determine, based on the sequence of RVs, a second transmission power for one or more second repetition occasions of the repetition occasions; and transmit, with the second transmission power, one or more second repetitions of the transport block via the one or more second repetition occasions.
 13. The wireless device of claim 12, wherein the one or more second repetition occasions correspond to one or more second RVs, of the sequence of RVs, not associated with the power offset value, and wherein the second transmission power is not determined based on the power offset value in response to the one or more second RVs not being associated with the power offset value.
 14. The wireless device of claim 13, wherein the one or more second RVs are not associated with the power offset value in response to the one or more second RVs corresponding to non-systematic bits of the RV sequence.
 15. The wireless device of claim 11, wherein each of the repetition occasions is associated with an RV of the sequence of RVs.
 16. The wireless device of claim 11, wherein the instructions further cause the wireless device to determine an RV, from the sequence of RVs, for each of the repetition occasions based on the sequence of RVs and an index of each of the repetition occasions.
 17. The wireless device of claim 11, wherein the one or more repetition occasions correspond to one or more RVs, of the sequence of RVs, associated with the power offset value, and wherein the transmission power is determined based on the power offset value in response to the one or more RVs being associated with the power offset value.
 18. The wireless device of claim 17, wherein the one or more RVs are associated with the power offset value in response to the one or more RVs corresponding to systematic bits of the RV sequence.
 19. The wireless device of claim 11, wherein a length of the sequence of RVs is equal to or less than the quantity of the repetition occasions.
 20. A non-transitory computer readable medium storing computer program instructions that, when executed by one or more processors of a wireless device, cause the wireless device to: receive a power offset value associated with a difference between transmission powers of different redundancy versions (RVs) of repetition occasions of a transport block; receive a downlink control information indicating: a sequence of RVs; and a quantity of the repetition occasions; determine, based on the power offset value and the RVs, a transmission power for one or more repetition occasions of the repetition occasions; and transmit, with the transmission power, one or more repetitions of the transport block via the one or more repetition occasions. 